Oracle® Insurance Policy Administration 9.5.0.0 E23638_01
You are here: Activities > Programs > Program Operations
Program Operations
Program Operations are defined system behaviors that occur based on changes made to program fields. The following information describes the behavior of OIPA when certain operations occur.
- Roll back: during this operation all active program activities are reversed, pending activities are shadowed and the program status reverts to PendingReady. A roll back can occur when a change is made to the value of a program field. When the Save button is clicked on the Program screen, a warning message displays verifying that the user wants to proceed. After the confirmation is clicked, the roll back occurs.
- Change Pending: indicates that a pending program activity has been updated in some way. This could be an action such as an update to a pending program activity field.
- Recycle: this occurs when the last active program activity is recycled. A warning is presented to the user for confirmation of the recycle operation. After the recycle is confirmed, the Activity Detail window will open. The user can make changes and when finished must click the OK button to close the window and process the recycle.
- Do Nothing: this indicates that no action is to be taken.
Change to a Program Date
OIPA handles changes to program dates differently depending on the status a program is in when a change is made to a fixed date field. The first action is to change the program status to Locked, making the program fields unavailable for update. The Locked status remains until the operation has completed processing.
An explanation of the operation behavior according to program status is shown below. This explains what is happening during the program lock, when OIPA is processing the date change.
Change a Program Start Date or Effective Date
- Pending Ready: OIPA performs the Do nothing operation. A lock is not necessary.
- Ready: OIPA shadows the Set Up activity and returns the program status to Pending Ready. A lock is not necessary.
- Pending: OIPA reverses the Set Up activity and returns the program status to Pending Ready. The effective date of the reversal is equal to the Set Up activity effective date. Program fields are locked until the operation completes processing.
- Active: OIPA reverses the Set Up activity and returns the program status to Pending Ready. The effective date of the reversal is equal to the Set Up activity effective date. Program fields are locked until the operation completes processing.
- Inactive: OIPA reverses the Set Up activity and returns the program status to Pending Ready. The effective date of the reversal is equal to the Set Up activity effective date. Program fields are locked until the operation completes processing.
- Terminated: OIPA reverses the Set Up activity and returns the program status to Pending Ready. The effective date of the reversal is equal to the Set Up activity effective date. Program fields are locked until the operation completes processing.
Change a Program End Date
- Pending Ready: OIPA performs the Do nothing operation. A lock is not necessary.
- Ready: OIPA performs the Do nothing operation. A lock is not necessary.
- Pending: there are two possible updates that can occur to an end date.
- Date is extended: OIPA performs the Do nothing operation. A lock is not necessary.
- Date is shortened: OIPA recycles the active program activity prior to the new end date. Program fields are locked down until processing is complete.
- Active: there are two possible updates that can occur to an end date.
- Date is extended: OIPA performs the Do nothing operation. A lock is not necessary.
- Date is shortened: OIPA recycles the active program activity prior to the new end date. Program fields are locked down until processing is complete.
- Inactive: there are two possible updates that can occur to an end date.
- Date is extended: OIPA recycles the active program activity prior to the new end date. Program fields are locked down until processing is complete.
- Date is shortened: OIPA recycles the active program activity prior to the new end date. Program fields are locked down until processing is complete.
- Terminated: there are two possible updates that can occur to an end date.
- Date is extended: OIPA recycles the active program activity prior to the new end date. Program fields are locked down until processing is complete.
- Date is shortened: OIPA recycles the program activity prior to the new end date. The program activity could be the scheduled program activity or the Set Up activity. Program fields are locked down until processing is complete.
Changes to Multiple Date Fields
When changes are made to multiple date fields at one time, OIPA follows the guidelines presented in the Change a Program Start Date or Effective Date section above. There are two exceptions: changes to a dynamic field and the end date or changes to dynamic fields only. In both cases, configuration determines the operation behavior.
Copyright © 2009, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices